interp: default to None for non-valued statements #1079
+97
−67
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here am using 'None' to refer to the functional programming concept of an empty result. I added
interp.EmptyResult
since that is far clearer than 'None', especially to users not familiar with functional programming jargon.Updates
*Interpreter.ast
to useval: EmptyResult
as the default, instead ofnew(interface{})
. UpdatesgenValue
to always returnnode.val
for a block statement where the last statement isvar x = 1
,x := 1
, orx = 1
.As a result, variable declarations and assignments return a value of
interp.EmptyResult
.